Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1588

reference: 292-tree-1
name: 1588
tree-preservation-order: undefined
292-tpo-1
uprn
address-text
point: POINT (-1.040678 50.897602)
geometry: MULTIPOLYGON (((-1.040636 50.897597,-1.040638 50.897605,-1.040644 50.897613,-1.040653 50.897619,-1.040665 50.897623,-1.040678 50.897624,-1.040691 50.897623,-1.040703 50.897619,-1.040713 50.897613,-1.040719 50.897606,-1.040721 50.897598,-1.040719 50.897589,-1.040713 50.897582,-1.040704 50.897576,-1.040692 50.897572,-1.040679 50.897570,-1.040654 50.897575,-1.040644 50.897581,-1.040638 50.897589,-1.040636 50.897597)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL